Can Not Send Attachments over 10 meg??  - Maybe????
When trying to send large attachments I receive the following error: This message exceeds the maximum message size allowed. Microsoft Exchange will not try to redeliver this message for you. Please make the message smaller -- by removing attachments, for example -- and try sending it again, or provide the following diagnostic text to your system administrator. _____ Sent by Microsoft Exchange Server 2007 Diagnostic information for administrators: Generating server: MAIL01.CARE.corp.com Marvin1@yahoo.com#550 5.2.3 RESOLVER.RST.RecipSizeLimit; message too large for this recipient ## Original message headers: Received: from PMAIL1.LCARE.corp.com ([fe80:0000:0000:0000:98e0:0124:225.83.79.178]) by nail01 ([101.112.6.98]) with mapi; Mon, 1 Mar 2010 21:12:14 -0600Content-Type: application/ms-tnef; name="winmail.dat"Content-Transfer-Encoding: binaryFrom: Marvin Mo <JDm\ralupen@CARE.COM>To: 'Marvin Mo' <Marvin1@yahoo.com>Date: Mon, 1 Mar 2010 21:11:52 -0600Subject: RE: TestThread-Topic: TestThread-Index: Acq5lA9eWKQvbbOdT6yEzOmjYcCbMAAIgUHQMessage-ID: <3387595AA4774145828EC2575B41E09E371A786987@CARE.corp.com>References: <838250.45572.qm@web110306.mail.gq1.yahoo.com>In-Reply-To: <838250.45572.qm@web110306.mail.gq1.yahoo.com>Accept-Language: en-USContent-Language: en-USX-MS-Has-Attach: yesX-MS-TNEF-Correlator: <3387595AA4774145828EC2575B41E09E371A786987@CARE.corp.com>MIME-Version: 1.0Since it shows that it is replying from yahoo mail servers it looks to me - they are kicking it back. But even when send a 20 meg file to Gmail ( which it should accept) we still get this message. Some of the NDR's dont show a receiving mail server. My question is - is it getting there or is our exchange 2007 server kicking it back?Here are our settings:GET-TRANSPORTCONFIG ClearCategories : TrueGenerateCopyOfDSNFor : {5.4.8, 5.4.6, 5.4.4, 5.2.4, 5.2.0, 5.1.4}InternalSMTPServers : {}JournalingReportNdrTo : <>MaxDumpsterSizePerStorageGroup : 45MBMaxDumpsterTime : 7.00:00:00MaxReceiveSize : 10MBMaxRecipientEnvelopeLimit : 5000MaxSendSize : 100MBTLSReceiveDomainSecureList : {}TLSSendDomainSecureList : {}VerifySecureSubmitEnabled : FalseVoicemailJournalingEnabled : TrueXexch50Enabled : TrueSend connector:AddressSpaces : {smtp:*;1}AuthenticationCredential : System.Management.Automation.PSCredentialComment :ConnectedDomains : {}ConnectionInactivityTimeOut : 00:10:00DNSRoutingEnabled : FalseDomainSecureEnabled : FalseEnabled : TrueForceHELO : FalseFqdn :HomeMTA : Microsoft MTAHomeMtaServerId : MAIL01Identity : IronmailIgnoreSTARTTLS : FalseIsScopedConnector : FalseIsSmtpConnector : TrueLinkedReceiveConnector :MaxMessageSize : 90MBName : IronmailOUTPort : 25ProtocolLoggingLevel : NoneRequireTLS : FalseSmartHostAuthMechanism : NoneSmartHosts : {[10.101.9.8]}SmartHostsString : [10.101.9.8]SourceIPAddress : 0.0.0.0SourceRoutingGroup : Exchange Routing Group (BWBGZMFD01QNBJO)SourceTransportServers : {MAIL01}UseExternalDNSServersEnabled : FalseI have used ADSIEDIT to the Global Settings - to 90 meg:Global Settings: Besides the above, another set of message size limits can impact Exchange Server 2007 recipients, but it's often overlooked when troubleshooting. This is the one in Exchange Server 2003 Global Settings | Message Delivery -> Properties.Is the message getting there? Is there another setting I missed - I have the users configured to be able to send 250 meg attachments.
March 2nd, 2010 10:56pm

You have a limit set somewhere. By the way, it's the message size that's limited, not just the attachment. Expect attachments to grow in size by 20% or more in e-mail messages due to encoding inefficiencies.-- Ed Crowley MVP"There are seldom good technological solutions to behavioral problems.". "D303M" wrote in message news:7e04be55-9a96-4d4b-9480-79624466da65...When trying to send large attachments I receive the following error: This message exceeds the maximum message size allowed. Microsoft Exchange will not try to redeliver this message for you. Please make the message smaller -- by removing attachments, for example -- and try sending it again, or provide the following diagnostic text to your system administrator. _____ Sent by Microsoft Exchange Server 2007 Diagnostic information for administrators: Generating server: MAIL01.CARE.corp.com Marvin1@yahoo.com#550 5.2.3 RESOLVER.RST.RecipSizeLimit; message too large for this recipient ## Original message headers: Received: from PMAIL1.LCARE.corp.com ([fe80:0000:0000:0000:98e0:0124:225.83.79.178]) by nail01 ([101.112.6.98]) with mapi; Mon, 1 Mar 2010 21:12:14 -0600Content-Type: application/ms-tnef; name="winmail.dat"Content-Transfer-Encoding: binaryFrom: Marvin Mo <JDm\ralupen@CARE.COM>To: 'Marvin Mo' <Marvin1@yahoo.com>Date: Mon, 1 Mar 2010 21:11:52 -0600Subject: RE: TestThread-Topic: TestThread-Index: Acq5lA9eWKQvbbOdT6yEzOmjYcCbMAAIgUHQMessage-ID: <3387595AA4774145828EC2575B41E09E371A786987@CARE.corp.com>References: <838250.45572.qm@web110306.mail.gq1.yahoo.com>In-Reply-To: <838250.45572.qm@web110306.mail.gq1.yahoo.com>Accept-Language: en-USContent-Language: en-USX-MS-Has-Attach: yesX-MS-TNEF-Correlator: <3387595AA4774145828EC2575B41E09E371A786987@CARE.corp.com>MIME-Version: 1.0Since it shows that it is replying from yahoo mail servers it looks to me - they are kicking it back. But even when send a 20 meg file to Gmail ( which it should accept) we still get this message. Some of the NDR's dont show a receiving mail server. My question is - is it getting there or is our exchange 2007 server kicking it back?Here are our settings:GET-TRANSPORTCONFIG ClearCategories : TrueGenerateCopyOfDSNFor : {5.4.8, 5.4.6, 5.4.4, 5.2.4, 5.2.0, 5.1.4}InternalSMTPServers : {}JournalingReportNdrTo : <>MaxDumpsterSizePerStorageGroup : 45MBMaxDumpsterTime : 7.00:00:00MaxReceiveSize : 10MBMaxRecipientEnvelopeLimit : 5000MaxSendSize : 100MBTLSReceiveDomainSecureList : {}TLSSendDomainSecureList : {}VerifySecureSubmitEnabled : FalseVoicemailJournalingEnabled : TrueXexch50Enabled : TrueSend connector:AddressSpaces : {smtp:*;1}AuthenticationCredential : System.Management.Automation.PSCredentialComment :ConnectedDomains : {}ConnectionInactivityTimeOut : 00:10:00DNSRoutingEnabled : FalseDomainSecureEnabled : FalseEnabled : TrueForceHELO : FalseFqdn :HomeMTA : Microsoft MTAHomeMtaServerId : MAIL01Identity : IronmailIgnoreSTARTTLS : FalseIsScopedConnector : FalseIsSmtpConnector : TrueLinkedReceiveConnector :MaxMessageSize : 90MBName : IronmailOUTPort : 25ProtocolLoggingLevel : NoneRequireTLS : FalseSmartHostAuthMechanism : NoneSmartHosts : {[10.101.9.8]}SmartHostsString : [10.101.9.8]SourceIPAddress : 0.0.0.0SourceRoutingGroup : Exchange Routing Group (BWBGZMFD01QNBJO)SourceTransportServers : {MAIL01}UseExternalDNSServersEnabled : FalseI have used ADSIEDIT to the Global Settings - to 90 meg:Global Settings: Besides the above, another set of message size limits can impact Exchange Server 2007 recipients, but it's often overlooked when troubleshooting. This is the one in Exchange Server 2003 Global Settings | Message Delivery -> Properties.Is the message getting there? Is there another setting I missed - I have the users configured to be able to send 250 meg attachments. Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."
Free Windows Admin Tool Kit Click here and download it now
March 2nd, 2010 11:02pm

I have checked every place I know of - Do you know anywhere else I can check for this size limit?
March 2nd, 2010 11:39pm

I files I have been testing with are 17-25 meg. The limits are set to 90 or 100 so there should be room for growth of the message. I have read everything I can find on where the bottleneck might be.
Free Windows Admin Tool Kit Click here and download it now
March 2nd, 2010 11:43pm

Check both Send and Receive Connectors. In the Management Console, that would be in the:Organization Configuration, Hub Transport, Send Connectors tabandServer Configration, Hub Transport, Receive ConnectorsAlso look at the topic:Managing Message Size Limitsin the Console help - lots of details there and Management Shell commands you can use to look at the various limits. SnoBoy
March 3rd, 2010 1:00am

I files I have been testing with are 17-25 meg. The limits are set to 90 or 100 so there should be room for growth of the message. I have read everything I can find on where the bottleneck might be. Though you have set the limits around 90M, the receive mail system may have their own limit.From yahoo support forum: 7.5M , and gmail about 25M.http://in.answers.yahoo.com/question/index?qid=20090921113825AAx78WDhttp://mail.google.com/support/bin/answer.py?hl=en&answer=8770How large the mail size you sent to the two address successful?Can you send very large attachment to other company? By the way, I don't think it's a good idea to send large attachment, you can use other file transfer system, like FTP.Sometime your ISP may also reject large mail from your system.Frank Wang
Free Windows Admin Tool Kit Click here and download it now
March 5th, 2010 6:29am

Do you know what limit the recipient has? What if you send it to yourself. Does that work? "D303M" wrote in message news:74be7a8b-f014-4f57-9ca1-497bbda37155...I files I have been testing with are 17-25 meg. The limits are set to 90 or 100 so there should be room for growth of the message. I have read everything I can find on where the bottleneck might be.
March 7th, 2010 1:21pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics